The Java6 compiler error should be easy to fix, I think you just need to use this statement:

  private static final AtomicReference<JSONParserConfiguration> GLOBAL_CONFIG  = 
        new AtomicReference<JSONParserConfiguration>(null);

AtomicReference may not be a good idea. This lib is not thread-safe, per design. Adding it here may give the impression the project is moving in that direction, which it is not.

There are no unit tests for the new/changed code.

If some maps need to be parsed with keep-null, and some maps without it, how would you get that behavior?

I'm not convinced yet that this is the best approach. It may be that this problem should be fixed in user code.

AtomicReference may not be a good idea. This lib is not thread-safe, per design. Adding it here may give the impression the project is moving in that direction, which it is not.

I have removed AtomicReference and am now directly using the class.

There are no unit tests for the new/changed code.

I have added unit tests to cover the new and modified code.

If some maps need to be parsed with keep-null, and some maps without it, how would you get that behavior?

This Global JSONParserConfiguration support enables user to have SystemWide setting for parsing Json. User can override it with new JSONParserConfiguration support when they dealing with to be parsed differently

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube Cloud